Move email related tasks in the same queue

[akatsoulas]

No description provided.

[Copilot]

PR Overview

This PR moves email-related tasks to the same "email" queue to consolidate processing and simplify configuration.

• Extended task_routes in the Celery configuration to include multiple email tasks.
• Added routes for tasks from various modules to be processed in the "email" queue.

Reviewed Changes

File	Description
kitsune/celery.py	Updated task_routes to include additional email processing tasks.

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

[akatsoulas]

This PR moves all the email related tasks to the same pod. Currently we have the following processing order:

• Emails are prepared in the email related tasks that run in multiple pods in the default queue
• The email tasks from the default queue trigger the send_messages multiple times (one from each task in each pod)
• Each worker in the pod that processes the email queue can run one of the send_messages
• This introduces a cross-queue task generation which also increases the load
• There's a potential for multiple emails because of tasks firing in quick succession and there's the potential for a task to run before the other has updated the database.

Even in the scenario that file locking and database updates happen in the right order and there are no issues, this PR will reduce the unnecessary load in the default queue